Input/output module with multi-channel switching capability

ABSTRACT

The present disclosure is directed to an input/output module. In some embodiments, the input/output module includes: a plurality of communication channels, each channel of the plurality of communication channels configured to connect to one or more field devices; switch fabric configured to selectively facilitate connectivity between an external control module and the one or more field devices via the plurality of communication channels; a serial communications port configured for connecting the input/output module to the control module in parallel with a second input/output module, the serial communications port configured for transmitting information between the input/output module and the control module; and a parallel communications port configured for separately connecting the input/output module to the control module, the parallel communications port configured for transmitting information between the input/output module and the control module, and transmitting information between the input/output module and the second input/output module.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority under 35 U.S.C. § 119(e) to U.S.Provisional Application Ser. No. 62/114,030, filed Feb. 9, 2015, andtitled “INPUT/OUTPUT MODULE WITH MULTI-CHANNEL SWITCHING CAPABILITY.”The present application is also a continuation-in-part of InternationalApplication No. PCT/US2013/053721, filed Aug. 6, 2013, and titled“SECURE INDUSTRIAL CONTROL SYSTEM.” The present application is also acontinuation-in-part under 35 U.S.C. § 120 of U.S. Patent ApplicationSer. No. 14/469,931, filed Aug. 27, 2014, and titled “SECURE INDUSTRIALCONTROL SYSTEM.” The present application is also a continuation-in-partunder 35 U.S.C. § 120 of U.S. patent application Ser. No. 14/446,412,filed Jul. 30, 2014, and titled “INDUSTRIAL CONTROL SYSTEM CABLE,” whichclaims priority under 35 U.S.C. § 119(e) to U.S. Provisional ApplicationSer. No. 62/021,438, filed Jul. 7, 2014, and titled “INDUSTRIAL CONTROLSYSTEM CABLE.” The present application is also a continuation-in-partunder 35 U.S.C. § 120 of U.S. patent application Ser. No. 14/519,066,filed Oct. 20, 2014, and titled “OPERATOR ACTION AUTHENTICATION IN ANINDUSTRIAL CONTROL SYSTEM.” The present application is also acontinuation-in-part under 35 U.S.C. § 120 of U.S. patent applicationSer. No. 14/519,047, filed Oct. 20, 2014, and titled “INDUSTRIAL CONTROLSYSTEM REDUNDANT COMMUNICATIONS/CONTROL MODULES AUTHENTICATION.” Thepresent application is also a continuation-in-part under 35 U.S.C. § 120of U.S. patent application Ser. No. 14/597,498, filed Jan. 15, 2015, andtitled “ELECTROMAGNETIC CONNECTOR,” which is a continuation under 35U.S.C. § 120 of U.S. patent application Ser. No. 13/341,143, filed Dec.30, 2011, and titled “ELECTROMAGNETIC CONNECTOR.” The presentapplication is also a continuation-in-part of International ApplicationNo. PCT/US2012/072056, filed Dec. 28, 2012 (having a priority date ofDec. 30, 2011), and titled “ELECTROMAGNETIC CONNECTOR ANDCOMMUNICATIONS/CONTROL SYSTEM/SWITCH FABRIC WITH SERIAL AND PARALLELCOMMUNICATIONS INTERFACES.” The present application is also acontinuation-in-part under 35 U.S.C. § 120 of U.S. patent applicationSer. No. 14/501,974, filed Sep. 30, 2014, and titled “SWITCH FABRICHAVING A SERIAL COMMUNICATIONS INTERFACE AND A PARALLEL COMMUNICATIONSINTERFACE,” which is a continuation under 35 U.S.C. § 120 of U.S. patentapplication Ser. No. 13/341,161, filed Dec. 30, 2011, and titled “SWITCHFABRIC HAVING A SERIAL COMMUNICATIONS INTERFACE AND A PARALLELCOMMUNICATIONS INTERFACE.” The present application is also acontinuation-in-part under 35 U.S.C. § 120 of U.S. patent applicationSer. No. 14/502,006, filed Sep. 30, 2014, and titled “COMMUNICATIONSCONTROL SYSTEM WITH A SERIAL COMMUNICATIONS INTERFACE AND A PARALLELCOMMUNICATIONS INTERFACE,” which is a continuation under 35 U.S.C. § 120of U.S. patent application Ser. No. 13/341,176, filed Dec. 30, 2011, andtitled “COMMUNICATIONS CONTROL SYSTEM WITH A SERIAL COMMUNICATIONSINTERFACE AND A PARALLEL COMMUNICATIONS INTERFACE.”

Each of the patent applications cross-referenced above is incorporatedherein by reference in its entirety.

BACKGROUND

Industrial control systems, such as standard industrial control systems(ICS) or programmable automation controllers (PAC), include varioustypes of control equipment used in industrial production, such assupervisory control and data acquisition (SCADA) systems, distributedcontrol systems (DCS), programmable logic controllers (PLC), andindustrial safety systems certified to safety standards such as IEC1508.These systems are used in industries including electrical, water andwastewater, oil and gas production and refining, chemical, food,pharmaceuticals and robotics. Using information collected from varioustypes of sensors to measure process variables, automated and/oroperator-driven supervisory commands from the industrial control systemcan be transmitted to various actuator devices such as control valves,hydraulic actuators, magnetic actuators, electrical switches, motors,solenoids, and the like. These actuator devices collect data fromsensors and sensor systems, open and close valves and breakers, regulatevalves and motors, monitor the industrial process for alarm conditions,and so forth.

In other examples, SCADA systems can use open-loop control with processsites that may be widely separated geographically. These systems useRemote Terminal Units (RTUs) to send supervisory data to one or morecontrol centers. SCADA applications that deploy RTU's include fluidpipelines, electrical distribution and large communication systems. DCSsystems are generally used for real-time data collection and continuouscontrol with high-bandwidth, low-latency data networks and are used inlarge campus industrial process plants, such as oil and gas, refining,chemical, pharmaceutical, food and beverage, water and wastewater, pulpand paper, utility power, and mining and metals. PLCs more typicallyprovide Boolean and sequential logic operations, and timers, as well ascontinuous control and are often used in stand-alone machinery androbotics. Further, ICE and PAC systems can be used in facility processesfor buildings, airports, ships, space stations, and the like (e.g., tomonitor and control Heating, Ventilation, and Air Conditioning (HVAC)equipment and energy consumption). As industrial control systems evolve,new technologies are combining aspects of these various types of controlsystems. For instance, PACs can include aspects of SCADA, DCS, and PLCs.

Within industrial control systems, communications/control modulestypically communicate with field devices (e.g., actuators, sensors, andthe like) via input/output modules. Technical advances have created ademand for enhanced connectivity between field devices and higher levelenterprise and industrial systems and a greater need for connectivityamong the devices themselves. In this regard, industrial systems areevolving in a similar manner to the “internet of things” but with muchhigher security, reliability, and throughput requirements. Robust andsecure input/output modules are needed to accommodate the emerging needsin industrial communications and control systems.

SUMMARY

The present disclosure is directed to an input/output module withmulti-channel switching capability that can be securely embedded withina communications backplane of an industrial control system. In someembodiments, the input/output module includes a plurality ofcommunication channels, where each of the channels is configured toconnect to one or more field devices. Switch fabric within theinput/output module selectively facilitates connectivity between anexternal control module and the one or more field devices via thecommunication channels. In order to facilitate interconnectivity via thecommunications backplane, the input/output module can further include aserial communications port and a parallel communications port. Theserial communications port can connect the input/output module to thecontrol module in parallel with at least one additional (second)input/output module, where the serial communications port transmitsinformation between the input/output module and the control module. Theparallel communications port can separately connect the input/outputmodule to the control module, where the parallel communications porttransmits information between the input/output module and the controlmodule, and also transmits information between the input/output moduleand the second input/output module.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

DRAWINGS

The Detailed Description is described with reference to the accompanyingfigures. The use of the same reference numbers in different instances inthe description and the figures may indicate similar or identical items.

FIG. 1 is a block diagram illustrating an input/output module inaccordance with embodiments of this disclosure.

FIG. 2 is a block diagram illustrating an industrial control system inaccordance with embodiments of this disclosure.

FIG. 3 is a block diagram illustrating a switch fabric in accordancewith embodiments of this disclosure.

FIG. 4 is an isometric view illustrating an industrial control system inaccordance with embodiments of this disclosure.

FIG. 5 is an isometric view of an input/output module coupled to asupport frame of the industrial control system illustrated in FIG. 4.

FIG. 6 is an isometric view of the input/output module illustrated inFIG. 4.

FIG. 7 is a side view of the input/output module illustrated in FIG. 4.

FIG. 8 is a cross-sectional side view of the input/output module and thesupport frame of the industrial control system illustrated in FIG. 4.

FIG. 9 is an isometric view of the support frame with an attachedcircuit board for the industrial control system illustrated in FIG. 4.

FIG. 10 is a block diagram illustrating an action authentication pathfor an industrial control system in accordance with embodiments of thisdisclosure.

FIG. 11 is a block diagram further illustrating the actionauthentication path shown in FIG. 10 in accordance with embodiments ofthis disclosure.

FIG. 12 is a flow diagram illustrating an example of a process forauthenticating an action request via an action authentication path, suchas the action authentication path shown in FIG. 10 or FIG. 11.

FIG. 13 is a block diagram illustrating a first input/output moduleperforming an authentication sequence with a second input/output modulein accordance with embodiments of this disclosure.

FIG. 14 is a flow diagram illustrating an example of an authenticationsequence performed by a first input/output module authenticating with asecond input/output module.

FIG. 15 is a flow diagram illustrating an example of a responsiveauthentication sequence performed by a second input/output module inresponse to an authentication sequence (e.g., as illustrated in FIG. 14)performed by a first input/output module.

DETAILED DESCRIPTION

Overview

Input/output (I/O) modules are used in industrial control systems toestablish communication between communications/control modules and fielddevices (e.g., actuators, sensors, and the like). Technical advanceshave created a demand for enhanced connectivity between field devicesand higher level enterprise and industrial systems and a greater needfor connectivity among the field devices themselves. In this regard,industrial systems are evolving in a similar manner to the “internet ofthings” but with much higher security, reliability, and throughputrequirements. Multi-port switches can be used to securely facilitateTCP/IP communication protocols, among others. However, a switch (e.g.,multi-port Ethernet switch) typically resides outside of an industrialcontrol system communications backplane and can be more vulnerable tosecurity threats as a result, possibly endangering devicescommunicatively coupled to the industrial control system via the switchand potentially placing the industrial control system as a whole atrisk.

An I/O module with multi-channel switching capability is disclosed,where the I/O module is configured to be securely embedded within acommunications backplane of an industrial control system. In someembodiments, the input/output module includes a plurality ofcommunication channels that can be configured to accommodate a varietyof communication protocols such as, but not limited to, Ethernet bus, H1field bus, Process Field Bus (PROFIBUS), Highway Addressable RemoteTransducer (HART) bus, Modbus, and Object Linking and Embedding forProcess Control Unified Architecture (OPC UA) communication standards.In some embodiments, two or more distinct communication standards can beconcurrently run on respective ones of the communication channels. Forexample, a first channel may run an OPC UA protocol while a secondchannel is running PROFIBUS, and so forth.

Example Implementations

FIG. 1 illustrates an I/O module 100 in accordance with embodiments ofthis disclosure. The I/O module 100 may include a plurality ofcommunication channels 102, such as Ethernet channels or the like. Thecommunication channels 102 can be used to connect to field deviceswithin a distributed control system, such as the industrial controlsystem 200 illustrated in FIG. 2 and described in further detail below.For example, each channel of the plurality of communication channels canbe configured to connect to one or more field devices 217, such asactuator devices 218 and sensor devices 220 including, but not limitedto, control valves, hydraulic actuators, magnetic actuators, motors,solenoids, electrical switches, transmitters, input sensors/receivers(e.g., illumination, radiation, gas, temperature, electrical, magnetic,and/or acoustic sensors), communications sub-busses, and the like.Switch fabric 104 within the I/O module can be configured to selectivelyfacilitate connectivity (e.g., transfer of information/data) between anexternal control module (e.g., communications/control module 214) andthe one or more field devices 217 via the plurality of communicationchannels 102.

In embodiments, the I/O module 100 includes a controller 106, such as amicroprocessor, microcontroller, ASIC, FPGA, or other single or multiplecore processing unit, configured to control the switch fabric 104. Forexample, the controller 106 can be configured to set arbitration rulesor priorities for the switch fabric and so forth. The controller 106 maybe configured to run/execute switch logic 110 (e.g., programinstructions) for controlling the switch fabric 104 from anon-transitory medium 108 (e.g., flash or solid-state memory device)that is communicatively coupled to the controller 106. In someembodiments, the I/O module 100 is operable as an OPC UA client and/orserver. For example, the controller 106 can be configured to run/executeswitch logic 110 that causes the controller 106 to implement OPC UAclient or server communications/control protocols.

In some embodiments, the controller 106 is configured to accommodatemultiple communication standards running concurrently on respectivechannels 102. For example, a first channel 102 can be configured by thecontroller 106 to send and receive information utilizing a PROFIBUSprotocol, and a second concurrently operable channel 102 can beconfigured by the controller 106 to send and receive informationutilizing an OPC UA protocol. In general, two or more communicationstandards may be concurrently implemented via respective channels 102,where the communication standards can include, but are not limited to,Ethernet bus, H1 field bus, PROFIBUS, HART bus, Modbus, and OPC UAcommunication standards.

The I/O module 100 may be further configured to synchronize timing ofconnected field devices 217 according to a timing protocol, such as theIEEE 1588 Precision Time Protocol (PTP). In this regard, the I/O module100 can implement a time distribution system, where the I/O module 100is a synchronization master device or an intermediate synchronizationdevice, the field devices 217 being lower than the I/O module 100 in thetiming control hierarchy.

In addition to establishing connectivity to the field device 217 viacommunication channels 102, the I/O module 100 can be further configuredto supply power to the field devices 217. In some embodiments, forexample, the I/O module 100 includes Power-Over-Ethernet (POE) circuitry120 configured to distribute incoming electrical power to one or more ofthe communication channels 102. Power may be supplied to the I/O modulevia a power backplane connection port 112 (e.g., E-core connection port)or an input jack 118. For example, the input jack 118 may be coupled toan external power source (e.g., local generator, backup power supply,etc.). In embodiments, the controller 106 can be configured toselectively enable power transfer via the communication channels 102.For example, POE functionality can be enabled for communication channels102 coupled to field devices 217 having POE capabilities (e.g., lowvoltage actuators 218, sensor 220, or communication devices). Where adevice 217 is configured to be powered by another source (e.g.,connection to the power backplane 234, internal/external battery, orother internal/external power source), the controller 106 may beconfigured to disable POE functionality of the respective communicationchannel 102 that is coupled with the device 217.

The I/O module 100 further includes one or more connection ports (e.g.,I-core connection ports) that facilitate interconnectivity with at leastone communications/control module 214 via a communications backplane(e.g., switch fabric 202). In some embodiments, the I/O module 100includes at least one serial communications port 114 and at least oneparallel communications port 116. The serial communications port 114 canconnect the I/O module 100 to the communications/control module 214 inparallel with at least one additional (second) I/O module 100. Forexample, the first and second I/O modules 100 can be concurrentlyconnected to the communications/control module 214 via respective serialinterface connections 204, where each I/O module 100 can receiveinformation from and transmit information to the communications/controlmodule 214 via the respective serial interface 204. The parallelcommunications port 116 can separately connect the I/O module 100 to thecommunications/control module 214 via a parallel communicationsinterface 206, where the I/O module 100 can receive information from andtransmit information to the communications/control module 214 via theparallel communications interface 206. The I/O module 100 can alsocommunicate with other I/O modules 100 via the parallel communicationsport 116 and interface 206.

In embodiments, one or more ports (e.g., serial communication port 114,parallel communication port 116, power backplane input 112, and/or inputjack 118) of the I/O module comprise or are coupled with electromagneticconnectors 207 of connector assemblies 208, such as those described inU.S. patent application Ser. No. 13/341,143 (Pub. No. US 2013/0170258)and Ser. No. 14/597,498, and in International Application No.PCT/US2012/072056 (International Pub. No. WO/2013/102069), all of whichare entirely incorporated herein by reference. The electromagneticconnectors 207 may be used in any application where it is desirable tocouple electrical circuits together for transmitting electrical signalsand/or electrical power from one circuit to another, while maintainingisolation between the circuits. The electromagnetic connectors 207 canbe used in applications including, but not necessarily limited to:industrial control systems/process control systems (e.g., to connect I/Omodules 100 with power and/or communications signal transmissioncircuitry), telecommunications (e.g., for audio, broadband, video,and/or voice transmission), information/data communications (e.g., forconnecting computer networking equipment, such as Ethernet equipment,modems, and so forth), computer hardware interconnection (e.g., forconnecting peripherals, such as joysticks, keyboards, mice, monitors,and so on), game consoles, test/measurement instruments, electricalpower connectors (e.g., for power transmission from AC mains), and thelike.

Each one of the electromagnetic connectors 207 is configured to form amagnetic circuit portion, which includes a core member and a coildisposed of (e.g., around or within) the core member. For the purposesof the present disclosure, it should be noted that “core member” is usedto refer to an incomplete part of a magnetic core, which is completed byanother core member when the electromagnetic connectors 207 are coupledtogether. Each electromagnetic connector 207 is configured to mate withanother electromagnetic connector 207 of a connector assembly 208 fortransmitting power and/or communications signals between components thatare connected via the electromagnetic connectors 207. For example, afirst core member of an electromagnetic connector 207 can be configuredto contact a second core member of another electromagnetic connector 207when the first electromagnetic connector 207 is mated with the secondelectromagnetic connector 207. In this manner, a coil of the firstelectromagnetic connector 207 can be tightly coupled to another coil ofthe second electromagnetic connector 207 with a magnetic circuit formedfrom the magnetic circuit portion of the first electromagnetic connector207 and the magnetic circuit portion of the second electromagneticconnector 207. The magnetic circuit is configured to induce a signal inone of the coils when the other coil is energized, allowing power and/orcommunications signals to be transmitted between components that areconnected via the electromagnetic connectors 207. In implementations,the coils can be tightly coupled (e.g., using an iron core to provide acoupling coefficient of about one (1)), critically coupled (e.g., whereenergy transfer in the passband is optimal), or overcoupled (e.g., wherea secondary coil is close enough to a primary coil to collapse theprimary coil's field).

The first core member may not necessarily be configured to contact thesecond core member when the first electromagnetic connector 207 is matedwith the second electromagnetic connector 207. Thus, an electromagneticconnector assembly 208 can be configured to transmit power and/orcommunications signals between components that are connected viaelectromagnetic connectors 207 using, for example, an interference fitconfiguration, where one coil is disposed around a first core member,while another coil is disposed within a second core member. Theinterference fit may be established using connectors having geometriesincluding, but not necessarily limited to: conical, concentric,eccentric, geometric, sloped for friction fit, and so forth.

In implementations, one or both of the core members and/or coils can beat least partially (e.g., fully or partially) mechanically encasedwithin a protective layer. The protective layer may be fabricated of anon-conductive/insulating material, such as a coating of thin filmplastic material. The protective layer (e.g., non-conductive/insulatingmaterial) can be applied using techniques including, but not necessarilylimited to: coating, painting, deposition, and so forth. For instance,the core member and coil of a first electromagnetic connector 207included within the I/O module 100 can be partially enclosed by a cover,while a second electromagnetic connector 207 included within the poweror communications backplane 202/234 may include a shaft configured tomate with the cover. In this manner, the cover and the shaft may beconfigured to ensure proper alignment of the first electromagneticconnector 207 with the second electromagnetic connector 207, whileprotecting the core members and/or the coil of the first electromagneticconnector 207 from corrosion, mechanical damage (e.g., fracture), and soforth. Encasement may be especially useful when a core member isconstructed from a brittle material. For instance, the core member canbe tightly encased in a protective layer formed of a plastic material.In this manner, when damage to the core member (e.g., cracks or breaksin the core member) occurs, the pieces of material can be maintained insubstantial contact with one another within the casing, thus damage tothe core material may not significantly decrease performance.

When the electromagnetic connectors 207 are mated, a core member of thepower or communications backplane 202/234 and a core member of the I/Omodule 100 may be configured to couple the coils via a magnetic circuit.The magnetic circuit may induce a signal in a coil of the I/O module 100when a respective coil of the power or communications backplane 202/234is energized (e.g., with the AC signal from a DC/AC converter). Thesignal induced in the coil of the I/O module 100 may be used to powerand/or furnish communications with circuitry of the module 100. Itshould be noted that while power or communications backplane 202/234 isdescribed as inducing a signal in the I/O module 100, thisimplementation is provided by way of example only and is not meant to berestrictive of the present disclosure. The magnetic circuit can also beused to induce a signal in a coil of the power or communicationsbackplane 202/234 when a coil of the I/O module 100 is energized topower and/or furnish communications with the power or communicationsbackplane 202/234 (e.g., transmission of communications via switchfabric 202 to the communications/control module 214). Further, the coilsincluded with mating electromagnetic connectors 207 may be energized inan alternating sequence (e.g., one after another) to providebidirectional communication, and so forth.

FIGS. 2-9 illustrate an industrial control system 200 in accordance withvarious embodiments of this disclosure. In embodiments, the industrialcontrol system 200 may comprise an industrial control system (ICS), aprogrammable automation controller (PAC), a supervisory control and dataacquisition (SCADA) system, a distributed control system (DCS),programmable logic controller (PLC), and industrial safety systemcertified to safety standards such as IEC1508, or the like. As shown inFIG. 2, the industrial control system 200 uses a communications controlarchitecture to implement a distributed control system that includes oneor more industrial elements (e.g., input/output modules, power modules,field devices, switches, workstations, and/or physical interconnectdevices) that are controlled or driven by one or more control elementsor subsystems distributed throughout the system. For example, one ormore I/O modules 100 may be connected to one or morecommunications/control modules 214.

The industrial control system 200 is configured to transmit data to andfrom the I/O modules 100. The I/O modules 100 can comprise inputmodules, output modules, and/or input and output modules. For instance,input modules can be used to receive information from input fielddevices 217 (e.g., sensors 218), while output modules can be used totransmit instructions to output field devices 217 (e.g., actuators 220).For example, an I/O module 100 can be connected to a process sensor formeasuring pressure in piping for a gas plant, a refinery, and so forthand/or connected to a process actuator for controlling a valve, binaryor multiple state switch, transmitter, or the like. Field devices 217are communicatively coupled with the 10 modules 100 either directly orvia network connections. For example, the field device 217 can beconnective via communication channels 102 accommodating one or moreTCP/IP standards. These devices 217 can include control valves,hydraulic actuators, magnetic actuators, motors, solenoids, electricalswitches, transmitters, input sensors/receivers (e.g., illumination,radiation, gas, temperature, electrical, magnetic, and/or acousticsensors) communications sub-busses, and the like.

The industrial control system 200 includes includes switch fabric 202facilitating interconnectivity of a communications backplane. Inembodiments, the switch fabric 202 comprises a serial communicationsinterface 204 and a parallel communications interface 206 for furnishingcommunications with a number of I/O modules 100. As shown in FIGS. 2-9,the I/O modules 100 can be connected to the industrial control system200 using one or more electromagnetic connectors 207. For instance, eachI/O module 100 can include or can be coupled to one or moreelectromagnetic connectors 207 or connector assemblies 208, with coremembers extending through coils. In some embodiments, the coils can beimplemented as planar windings on a circuit board. When included in anI/O module 100, the circuit board can be “floated” against a partialspring load, allowing for some movement of the circuit boardperpendicular to the plane of a core member, e.g., to compensate fortolerances across the circuit board. For example, a self-holding springloading mechanism can be provided in the module to provide a constantdownward pressure to facilitate mating of the electromagneticconnection, compensating for stacked tolerances of the module, PCB, andbaseplate/support frame and ensuring a constant mating of both halves ofan electromagnetic connector assembly.

In some embodiments, a “tongue and groove” configuration can be usedthat provides inherent fastening and support in three planes. Forexample, a printed circuit board included within an I/O module 100 canbe configured to slide along and between two track segments in adirection perpendicular to the plane of a core member. Further, a coremember can be mechanically isolated from (e.g., not touching) thecircuit board. It should be noted that the implementation with planarprimary and secondary windings is provided by way of example only and isnot necessarily meant to be restrictive of the present disclosure. Thus,other implementations can use other coil configurations, such as wirewound coils, and so forth. For example, the primary coil may comprise aplanar winding, and the secondary coil may comprise a wire wound coil.Further, the primary coil may comprise a wire wound coil, and thesecondary coil may comprise a planar winding. In other implementations,primary and secondary coils may both comprise wire wound coils.

FIG. 3 shows an embodiment of the switch fabric 202. The switch fabric202 may be configured for use with any systems technology, such astelecommunications network technology, computer network technology,process control systems technology, and so forth. For example, theswitch fabric 202 may be used with a distributed control systemcomprised of controller elements and subsystems, where the subsystemsare controlled by one or more controllers distributed throughout thesystem. The switch fabric 202 includes a serial communications interface204 and a parallel communications interface 206 for furnishingcommunications with a number of slave devices.

The serial communications interface 204 may be implemented using a groupof connectors connected in parallel with one another. In someembodiments, the connectors may be configured as electromagneticconnectors 207/connector assemblies 208 (e.g., as previously described).For example, the serial communications interface 204 may be implementedusing a multidrop bus 210, or the like. In implementations, themultidrop bus 210 may be used for configuration and diagnostic functionsof the I/O modules 100/slave devices. The parallel communicationsinterface 206 allows multiple signals to be transmitted simultaneouslyover multiple dedicated high speed parallel communication channels. Forinstance, the parallel communications interface 206 may be implementedusing a cross switch 212, or the like.

In an embodiment shown in FIG. 3, the parallel communications interface206 may be implemented using a four (4) wire full duplex cross switch212 with a dedicated connection to each I/O module 100/slave device. Inimplementations, each connection may be furnished using one or moreelectromagnetic connectors 207/connector assemblies 208 (e.g., aspreviously described). The cross switch 212 can be implemented as aprogrammable cross switch connecting point-to-point busses and allowingtraffic between the I/O modules 100/slave devices. The cross switch 212may be configured by a master device, such as a communications/controlmodule 214. For example, the communications/control module 214/masterdevice may configure one or more sets of registers included in the crossswitch 212 to control traffic between the I/O modules 100/slave devices.In implementations, a communications/control module 214/master devicemay comprise a rule set dictating how the I/O modules 100/slave devicesare interconnected. For example, a communications/control module214/master device may comprise a set of registers, where each registerdefines the operation of a particular switch (e.g., with respect to howpackets are forwarded, and so forth). Thus, the cross switch 212 may notnecessarily auto-configure, instead implementing a configurationprovided by a communications/control module 214/the master device.However, this configuration is provided by way of example only and isnot meant to be restrictive of the present disclosure. Thus, in otherimplementations, the cross switch 212 may auto-configure.

The parallel communications interface 206 may be used for datacollection from the I/O modules 100/slave devices. Further, because eachI/O module 100/slave device has its own private bus to thecommunications/control module 214/master device, each I/O module100/slave device can communicate with the communications/control module214 at the same time. Thus, the total response time for the industrialcontrol system 200/switch fabric 202 may be limited to that of theslowest I/O module 100/slave device, instead of the sum of all slavedevices, as in the case of a typical multidrop bus.

In implementations, the switch fabric 202, the serial communicationsinterface 204, and the parallel communications interface 206 may beimplemented in a single, monolithic circuit board 216, e.g., withmultiple E-shaped core members of electromagnetic connectors 207extending through the circuit board 216, as shown in FIG. 9. Inimplementations, the core members may be mechanically isolated from thecircuit board 216 (e.g., not touching the circuit board 216). However,this configuration is provided by way of example only and is not meantto be restrictive of the present disclosure. Thus, the serialcommunications interface 204 and the parallel communications interface206 may be implemented using different arrangements of multiplecomponents, such as multiple discrete semiconductor devices forimplementing the serial communications interface 204 and the parallelcommunications interface 206 separately, and so forth.

The switch fabric 202 may be configured for connecting one or more I/Omodules 100 (e.g., as slave devices) and transmitting data to and fromthe I/O modules 100. The I/O modules 100 may comprise input modules,output modules, and/or input and output modules. For instance, inputmodules can be used to receive information from input instruments in theprocess or the field, while output modules can be used to transmitinstructions to output instruments in the field. For example, an I/Omodule 100 can be connected to a process sensor, such as a sensor 218for measuring pressure in piping for a gas plant, a refinery, and soforth. In implementations, the I/O modules 100 can be used theindustrial control system 200 collect data in applications including,but not necessarily limited to critical infrastructure and/or industrialprocesses, such as product manufacturing and fabrication, utility powergeneration, oil, gas, and chemical refining; pharmaceuticals, food andbeverage, pulp and paper, metals and mining and facility and largecampus industrial processes for buildings, airports, ships, and spacestations (e.g., to monitor and control Heating, Ventilation, and AirConditioning (HVAC) equipment and energy consumption).

In implementations, an I/O module 100 can be configured to convertanalog data received from the sensor to digital data (e.g., usingAnalog-to-Digital Converter (ADC) circuitry, and so forth). An I/Omodule 100 can also be connected to one or more process actuators 220such as a motor or a regulating valve or an electrical relay and otherforms of actuators and configured to control one or more operatingcharacteristics of the motor, such as motor speed, motor torque, orposition of the regulating valve or state of the electrical relay and soforth. Further, the I/O module 100 can be configured to convert digitaldata to analog data for transmission to the actuator 220 (e.g., usingDigital-to-Analog (DAC) circuitry, and so forth). In implementations,one or more of the I/O modules 100 can comprise a communications moduleconfigured for communicating via a communications sub-bus, such as anEthernet bus, an H1 field bus, a PROFIBUS, a HART bus, a Modbus, an OPCUA bus, and so forth. Further, two or more I/O modules 100 can be usedto provide fault tolerant and redundant connections for various fielddevices 217 such as control valves, hydraulic actuators, magneticactuators, motors, solenoids, electrical switches, transmitters, inputsensors/receivers (e.g., illumination, radiation, gas, temperature,electrical, magnetic, and/or acoustic sensors) communicationssub-busses, and the like.

Each I/O module 100 may be provided with a unique identifier (ID) fordistinguishing one I/O module 100 from another I/O module 100. Inimplementations, an I/O module 100 may be identified by its ID when itis connected to the industrial control system 200. Multiple I/O modules100 can be used with the industrial control system 200 to provideredundancy. For example, two or more I/O modules 100 can be connected tothe sensor 218, actuator 220, or any other field device 217, as shown inFIG. 2. Each I/O module 100 can include one or more ports 222 furnishinga physical connection to hardware and circuitry included with the I/Omodule 100, such as a Printed Circuit Board (PCB) 224, and so forth.

One or more of the I/O modules 100 can include an interface forconnecting to other networks including, but not necessarily limited to:a wide-area cellular telephone network, such as a 3G cellular network, a4G cellular network, or a Global System for Mobile communications (GSM)network; a wireless computer communications network, such as a Wi-Finetwork (e.g., a Wireless LAN (WLAN) operated using IEEE 802.11 networkstandards); a Personal Area Network (PAN) (e.g., a Wireless PAN (WPAN)operated using IEEE 802.15 network standards); a Wide Area Network(WAN); an intranet; an extranet; an internet; the Internet; and so on.Further, one or more of the I/O modules 100 can include a connection forconnecting an I/O module 100 to a computer bus, and so forth.

The communications/control modules 214 can be used to monitor andcontrol the I/O modules 100, and to connect two or more I/O modules 100together. In embodiments of the disclosure, a communications/controlmodule 214 can update a routing table when an I/O module 100 isconnected to the industrial control system 200 based upon a unique IDfor the I/O module 100. Further, when multiple redundant I/O modules 100are used, each communications/control module 214 can implement mirroringof informational databases regarding the I/O modules 100 and update themas data is received from and/or transmitted to the I/O modules 100. Insome embodiments, two or more communications/control module 214 are usedto provide redundancy. For added security, the communications/controlmodule 214 can be configured to perform an authentication sequence orhandshake to authenticate one another at predefined events or timesincluding such as startup, reset, installation of a new control module214, replacement of a communications/control module 214, periodically,scheduled times, and the like. The I/O modules 100 can also beconfigured to perform an authentication sequence or “handshake,” asillustrated in FIGS. 10-15 and described in further detail below.

Data transmitted using the switch fabric 202 may be packetized, i.e.,discrete portions of the data may be converted into data packetscomprising the data portions along with network control information, andso forth. The industrial control system 200/switch fabric 202 may useone or more protocols for data transmission, including a bit-orientedsynchronous data link layer protocol such as High-Level Data LinkControl (HDLC). In a specific instance, the industrial control system200/switch fabric 202 may implement HDLC according to an InternationalOrganization for Standardization (ISO) 13239 standard, or the like.Further, two or more communications/control modules 214 can be used toimplement redundant HDLC. However, it should be noted that HDLC isprovided by way of example only and is not meant to be restrictive ofthe present disclosure. Thus, the industrial control system 200 may useother various communications protocols in accordance with the presentdisclosure.

One or more of the communications/control modules 214 may be configuredfor exchanging information with components used for monitoring and/orcontrolling the instrumentation connected to the switch fabric 202 viathe I/O modules 100, such as one or more control loop feedbackmechanisms/controllers 226. In implementations, a controller 226 can beconfigured as a microcontroller/Programmable Logic Controller (PLC), aProportional-Integral-Derivative (PID) controller, and so forth. One ormore of the communications/control modules 214 may include a networkinterface 228 for connecting the industrial control system 200 to acontroller 226 via a network 230. In implementations, the networkinterface 228 may be configured as a Gigabit Ethernet interface forconnecting the switch fabric 202 to a Local Area Network (LAN). Further,two or more communications/control modules 214 can be used to implementredundant Gigabit Ethernet. However, it should be noted that GigabitEthernet is provided by way of example only and is not meant to berestrictive of the present disclosure. Thus, the network interface 228may be configured for connecting the industrial control system 200 toother various networks, including but not necessarily limited to: awide-area cellular telephone network, such as a 3G cellular network, a4G cellular network, or a Global System for Mobile communications (GSM)network; a wireless computer communications network, such as a Wi-Finetwork (e.g., a Wireless LAN (WLAN) operated using IEEE 802.11 networkstandards); a Personal Area Network (PAN) (e.g., a Wireless PAN (WPAN)operated using IEEE 802.15 network standards); a Wide Area Network(WAN); an intranet; an extranet; an internet; the Internet; and so on.Additionally, the network interface 228 may be implemented usingcomputer bus. For example, the network interface 228 can include aPeripheral Component Interconnect (PCI) card interface, such as a MiniPCI interface, and so forth. Further, the network 230 may be configuredto include a single network or multiple networks across different accesspoints.

The industrial control system 200 may include one or more power modules232 for supplying electrical power to field devices via the I/O modules100. One or more of the power modules 232 may include an AC-to-DC(AC/DC) converter for converting Alternating Current (AC) (e.g., assupplied by AC mains, and so forth) to Direct Current (DC) fortransmission to a field device, such as the motor 220 (e.g., in animplementation where the motor 220 comprises a DC motor). Two or morepower modules 232 can be used to provide redundancy. For example, asshown in FIG. 2, two power modules 232 can be connected to each of theI/O modules 100 using a separate (redundant) power backplane 234 foreach power module 232. In implementations, power backplane 234 may beconnected to one or more of the I/O modules 100 using electromagneticconnectors 207/connector assemblies 208 (e.g., as previously described).In implementations, power backplane 234 may be included with circuitboard 216, along with serial communications interface 204 and parallelcommunications interface 206.

The industrial control system 200 can receive electrical power frommultiple sources. For example, AC power may be supplied from a powergrid (e.g., using high voltage power from AC mains). AC power can alsobe supplied using local power generation (e.g., an on-site turbine ordiesel local power generator). A power supply may distribute electricalpower from the power grid to automation equipment of the industrialcontrol system 200, such as controllers, I/O modules, and so forth. Apower supply can also be used to distribute electrical power from thelocal power generator to the industrial control system equipment. Theindustrial control system 200 can also include additional (backup) powersupplies configured to store and return DC power using multiple batterymodules. For example, a power supply may function as a UPS. In someembodiments, multiple power supplies can be distributed (e.g.,physically decentralized) within the industrial control system 200.

The industrial control system 200 may be implemented using a supportframe 236. The support frame 236 may be used to support and/orinterconnect the communications/control module(s) 214, the powermodule(s) 232, the switch fabric 202, the power backplane(s) 234, and/orthe I/O modules 100. For example, the switch fabric 202 may be comprisedof a circuit board 216. The circuit board 216 may be mounted to thesupport frame 236 using a fastener such as, for example, double sidedtape, adhesive, or mechanical fasteners (e.g., screws, bolts, etc.).Additionally, the core members of the electromagnetic connectors 207 maybe mounted to the support frame 236 using a fastener such as, forexample, double sided tape, adhesive, or mechanical fasteners (e.g.,screws, bolts, etc.). In some implementations, a template may be used toposition the core members in the channel of the support frame 236. Inimplementations, the top surface of a core member may be substantiallyflush with a top surface of the circuit board 216. In otherimplementations, the top surface of a core member may be recessed somedistance below a top surface of the circuit board 216 (e.g., by aboutone millimeter (1 mm)) and/or may extend above a top surface of thecircuit board 216.

The support frame 236 may include slots 238 to provide registration forthe I/O modules 100, such as for aligning connectors (e.g.,electromagnetic connectors 207) of the I/O modules 100 with connectors(e.g., electromagnetic connectors 207) included with the circuit board216 and/or connectors (e.g., electromagnetic connectors 207) of a powerbackplane 234. For example, an I/O module 100 may include connectors 240having tabs/posts 242 for inserting into slots 238 and providingalignment of the I/O module 100 with respect to the circuit board 216.In implementations, one or more of the connectors 240 may be constructedfrom a thermally conductive material (e.g., metal) connected to athermal plane of PCB 224 to conduct heat generated by components of thePCB 224 away from the PCB 224 and to the support frame 236, which itselfmay be constructed of a thermally conductive material (e.g., metal).Further, the industrial control system 200 may associate a uniquephysical ID with each physical slot 238 to uniquely identify each I/Omodule 100 coupled with a particular slot 238. For example, the ID of aparticular slot 238 can be associated with an I/O module 100 coupledwith the slot 238 and/or a second ID uniquely associated with the I/Omodule 100. Further, the ID of a particular I/O module 100 can be usedas the ID for a slot 238 when the I/O module 100 is coupled with theslot 238. The support frame 236 can be constructed for cabinet mounting,rack mounting, wall mounting, and so forth.

It should be noted that while the industrial control system 200 isdescribed in the accompanying figures as including one switch fabric202, more than one switch fabric 202 may be provided with industrialcontrol system 200. For example, two or more switch fabrics 202 may beused with the industrial control system 200 (e.g., to provide physicalseparation between redundant switch fabrics 202, and so forth). Each oneof the switch fabrics 202 may be provided with its own support frame236. Further, while both the serial communications interface 204 and theparallel communications interface 206 are described as included in asingle switch fabric 202, it will be appreciated that physicallyseparate switch fabrics may be provided, where one switch fabricincludes the serial communications interface 204, and another switchfabric includes the parallel communications interface 206.

The control elements/subsystems and/or industrial elements (e.g., theI/O modules 100, the communications/control modules 214, the powermodules 232, and so forth) can be connected together by one or morebackplanes. For example, as described above, communications/controlmodules 214 can be connected to I/O modules 100 by a communicationsbackplane (e.g., switch fabric 202). Further, power modules 232 can beconnected to I/O modules 100 and/or to communications/control modules214 by a power backplane 234. In some embodiments, physical interconnectdevices (e.g., switches, connectors, or cables such as, but not limitedto, those described in U.S. patent application Ser. No. 14/446,412,hereby incorporated by reference in its entirety) are used to connect tothe I/O modules 100, the communications/control modules 214, the powermodules 232, and possibly other industrial control system equipment. Forexample, a cable can be used to connect a communications/control module214 to a network 230, another cable can be used to connect a powermodule 232 to a power grid, another cable can be used to connect a powermodule 232 to a local power generator, and so forth.

In some embodiments, the industrial control system 200 implements asecure control system, as described in U.S. Patent Application SerialNo. 14/469,931 and International Application No. PCT/US2013/053721,which are entirely incorporated herein by reference. For example, theindustrial control system 200 includes a security credential source(e.g., a factory) and a security credential implementer (e.g., a keymanagement entity). The security credential source is configured togenerate a unique security credential (e.g., a key, a certificate, etc.,such as a unique identifier, and/or a security credential). The securitycredential implementer is configured to provision the controlelements/subsystems and/or industrial elements (e.g., cables, devices217, I/O modules 100, communications/control modules 214, power modules232, and so forth) with a unique security credential generated by thesecurity credential source.

Multiple (e.g., every) device 217, I/O module 100,communications/control module 214, power module 232, physicalinterconnect devices, etc., of the industrial control system 200 can beprovisioned with security credentials for providing security at multiple(e.g., all) levels of the industrial control system 200. Still further,the control elements/subsystems and/or industrial elements including thesensors and/or actuators and so forth, can be provisioned with theunique security credentials (e.g., keys, certificates, etc.) duringmanufacture (e.g., at birth), and can be managed from birth by a keymanagement entity of the industrial control system 200 for promotingsecurity of the industrial control system 200.

In some embodiments, communications between the controlelements/subsystems and/or industrial elements including the sensorsand/or actuators and so forth, of the industrial control system 200includes an authentication process. The authentication process can beperformed for authenticating control elements/subsystem and/orindustrial elements including the sensors and/or actuators and so forth,implemented in the industrial control system 200. Further, theauthentication process can utilize security credentials associated withthe element and/or physical interconnect device for authenticating thatelement and/or physical interconnect device. For example, the securitycredentials can include encryption keys, certificates (e.g., public keycertificates, digital certificates, identity certificates, securitycertificates, asymmetric certificates, standard certificates,non-standard certificates) and/or identification numbers.

In implementations, multiple control elements/subsystems and/orindustrial elements of the industrial control system 200 are provisionedwith their own unique security credentials. For example, each element ofthe industrial control system 200 may be provisioned with its own uniqueset(s) of certificates, encryption keys and/or identification numberswhen the element is manufactured (e.g., the individual sets of keys andcertificates are defined at the birth of the element). The sets ofcertificates, encryption keys and/or identification numbers areconfigured for providing/supporting strong encryption. The encryptionkeys can be implemented with standard (e.g., commercial off-the-shelf(COTS)) encryption algorithms, such as National Security Agency (NSA)algorithms, National Institute of Standards and Technology (NIST)algorithms, or the like.

Based upon the results of the authentication process, the element beingauthenticated can be activated, partial functionality of the element canbe enabled or disabled within the industrial control system 200,complete functionality of the element can be enabled within theindustrial control system 200, and/or functionality of the elementwithin the industrial control system 200 can be completely disabled(e.g., no communication facilitated between that element and otherelements of the industrial control system 200).

In embodiments, the keys, certificates and/or identification numbersassociated with an element of the industrial control system 200 canspecify the original equipment manufacturer (OEM) of that element. Asused herein, the term “original equipment manufacturer” or “OEM” can bedefined as an entity that physically manufactures the device (e.g.,element) and/or a supplier of the device such as an entity thatpurchases the device from a physical manufacturer and sells the device.Thus, in embodiments, a device can be manufactured and distributed(sold) by an OEM that is both the physical manufacturer and the supplierof the device. However, in other embodiments, a device can bedistributed by an OEM that is a supplier, but is not the physicalmanufacturer. In such embodiments, the OEM can cause the device to bemanufactured by a physical manufacturer (e.g., the OEM can purchase,contract, order, etc. the device from the physical manufacturer).

Additionally, where the OEM comprises a supplier that is not thephysical manufacturer of the device, the device can bear the brand ofthe supplier instead of brand of the physical manufacturer. For example,in embodiments where an element (e.g., a communications/control module214 or an I/O module 100) is associated with a particular OEM that is asupplier but not the physical manufacturer, the element's keys,certificates and/or identification numbers can specify that origin.During authentication of an element of the industrial control system200, when a determination is made that an element being authenticatedwas manufactured or supplied by an entity that is different than the OEMof one or more other elements of the industrial control system 200, thenthe functionality of that element can be at least partially disabledwithin the industrial control system 200. For example, limitations canbe placed upon communication (e.g., data transfer) between that elementand other elements of the industrial control system 200, such that theelement cannot work/function within the industrial control system 200.When one of the elements of the industrial control system 200 requiresreplacement, this feature can prevent a user of the industrial controlsystem 200 from unknowingly replacing the element with a non-homogenouselement (e.g., an element having a different origin (a different OEM)than the remaining elements of the industrial control system 200) andimplementing the element in the industrial control system 200. In thismanner, the techniques described herein can prevent the substitution ofelements of other OEM's into a secure industrial control system 200. Inone example, the substitution of elements that furnish similarfunctionality in place of elements provided by an originating OEM can beprevented, since the substituted elements cannot authenticate andoperate within the originating OEM's system. In another example, a firstreseller can be provided with elements having a first set of physicaland cryptographic labels by an originating OEM, and the first reseller'selements can be installed in an industrial control system 200. In thisexample, a second reseller can be provided with elements having a second(e.g., different) set of physical and cryptographic labels by the sameoriginating OEM. In this example, the second reseller's elements may beprevented from operating within the industrial control system 200, sincethey may not authenticate and operate with the first reseller'selements. However, it should also be noted that the first reseller andthe second reseller may enter into a mutual agreement, where the firstand second elements can be configured to authenticate and operate withinthe same industrial control system 200. Further, in some embodiments, anagreement between resellers to allow interoperation can also beimplemented so the agreement only applies to a specific customer, groupof customers, facility, etc.

In another instance, a user can attempt to implement an incorrectlydesignated (e.g., mismarked) element within the industrial controlsystem 200. For example, the mismarked element can have a physicalindicia marked upon it which falsely indicates that the element isassociated with the same OEM as the OEM of the other elements of theindustrial control system 200. In such instances, the authenticationprocess implemented by the industrial control system 200 can cause theuser to be alerted that the element is counterfeit. This process canalso promote improved security for the industrial control system 200,since counterfeit elements are often a vehicle by which malicioussoftware can be introduced into the industrial control system 200. Inembodiments, the authentication process provides a secure air gap forthe industrial control system 200, ensuring that the secure industrialcontrol system is physically isolated from insecure networks.

In implementations, the secure industrial control system 200 includes akey management entity. The key management entity can be configured formanaging cryptographic keys (e.g., encryption keys) in a cryptosystem.This managing of cryptographic keys (e.g., key management) can includethe generation, exchange, storage, use, and/or replacement of the keys.For example, the key management entity is configured to serve as asecurity credentials source, generating unique security credentials(e.g., public security credentials, secret security credentials) for theelements of the industrial control system 200. Key management pertainsto keys at the user and/or system level (e.g., either between users orsystems).

In embodiments, the key management entity comprises a secure entity suchas an entity located in a secure facility. The key management entity canbe remotely located from the I/O modules 100, the communications/controlmodules 214, and the network 230. For example, a firewall can separatethe key management entity from the control elements or subsystems andthe network 230 (e.g., a corporate network). In implementations, thefirewall can be a software and/or hardware-based network security systemthat controls ingoing and outgoing network traffic by analyzing datapackets and determining whether the data packets should be allowedthrough or not, based on a rule set. The firewall thus establishes abarrier between a trusted, secure internal network (e.g., the network230) and another network that is not assumed to be secure and trusted(e.g., a cloud and/or the Internet). In embodiments, the firewall allowsfor selective (e.g., secure) communication between the key managemententity and one or more of the control elements or subsystems and/or thenetwork 230. In examples, one or more firewalls can be implemented atvarious locations within the industrial control system 200. For example,firewalls can be integrated into switches and/or workstations of thenetwork 230.

The secure industrial control system 200 can further include one or moremanufacturing entities (e.g., factories). The manufacturing entities canbe associated with original equipment manufacturers (OEMs) for theelements of the industrial control system 200. The key management entitycan be communicatively coupled with the manufacturing entity via anetwork (e.g., a cloud). In implementations, when the elements of theindustrial control system 200 are being manufactured at one or moremanufacturing entities, the key management entity can be communicativelycoupled with (e.g., can have an encrypted communications pipeline to)the elements. The key management entity can utilize the communicationspipeline for provisioning the elements with security credentials (e.g.,inserting keys, certificates and/or identification numbers into theelements) at the point of manufacture.

Further, when the elements are placed into use (e.g., activated), thekey management entity can be communicatively coupled (e.g., via anencrypted communications pipeline) to each individual element worldwideand can confirm and sign the use of specific code, revoke (e.g., remove)the use of any particular code, and/or enable the use of any particularcode. Thus, the key management entity can communicate with each elementat the factory where the element is originally manufactured (e.g.,born), such that the element is born with managed keys. A masterdatabase and/or table including all encryption keys, certificates and/oridentification numbers for each element of the industrial control system200 can be maintained by the key management entity. The key managemententity, through its communication with the elements, is configured forrevoking keys, thereby promoting the ability of the authenticationmechanism to counter theft and re-use of components.

In implementations, the key management entity can be communicativelycoupled with one or more of the control elements/subsystems, industrialelements, and/or the network 230 via another network (e.g., a cloudand/or the Internet) and firewall. For example, in embodiments, the keymanagement entity can be a centralized system or a distributed system.Moreover, in embodiments, the key management entity can be managedlocally or remotely. In some implementations, the key management entitycan be located within (e.g., integrated into) the network 230 and/or thecontrol elements or subsystems. The key management entity can providemanagement and/or can be managed in a variety of ways. For example, thekey management entity can be implemented/managed: by a customer at acentral location, by the customer at individual factory locations, by anexternal third party management company and/or by the customer atdifferent layers of the industrial control system 200, and at differentlocations, depending on the layer.

Varying levels of security (e.g., scalable, user-configured amounts ofsecurity) can be provided by the authentication process. For example, abase level of security can be provided which authenticates the elementsand protects code within the elements. Other layers of security can beadded as well. For example, security can be implemented to such a degreethat a component, such as the communications/control module 214 or theI/O module 100, cannot power up without proper authentication occurring.In implementations, encryption in the code is implemented in theelements, while security credentials (e.g., keys and certificates) areimplemented on the elements. Security can be distributed (e.g., flows)through the industrial control system 200. For example, security canflow through the industrial control system 200 all the way to an enduser, who knows what a module is designed to control in that instance.In embodiments, the authentication process provides encryption,identification of devices for secure communication and authentication ofsystem hardware or software components (e.g., via digital signature).

In implementations, the authentication process can be implemented toprovide for and/or enable interoperability within the secure industrialcontrol system 200 of elements manufactured and/or supplied by differentmanufacturers/vendors/suppliers (e.g., OEMs). For example, selective(e.g., some) interoperability between elements manufactured and/orsupplied by different manufacturers/vendors/suppliers can be enabled. Inembodiments, unique security credentials (e.g., keys) implemented duringauthentication can form a hierarchy, thereby allowing for differentfunctions to be performed by different elements of the industrialcontrol system 200.

The communication links connecting the components of the industrialcontrol system 200 can further employ data packets, such as runt packets(e.g., packets smaller than sixty-four (64) bytes), placed (e.g.,injected and/or stuffed) therein, providing an added level of security.The use of runt packets increases the level of difficulty with whichoutside information (e.g., malicious content such as false messages,malware (viruses), data mining applications, etc.) can be injected ontothe communications links. For example, runt packets can be injected ontoa communication link within gaps between data packets transmitted fromthe I/O module 100 to one or more field devices 217 via one or more ofthe communication channels 102 to hinder an external entity's ability toinject malicious content onto the communication link.

As shown in FIGS. 10 and 11, the I/O module 100 or any other industrialelement/controller 306 (e.g., communications/control module 214, fielddevices 217, physical interconnect devices, switches, power modules 232,etc.) can be at least partially operated according to requests/commandsfrom an action originator 302. In implementations, the action originator302 includes an operator interface 308 (e.g., SCADA or HMI), anengineering interface 310 including an editor 312 and a compiler 314, alocal application 320, a remote application 316 (e.g., communicatingthrough a network 318 via a local application 320), or the like. In theauthentication path 300 illustrated in FIGS. 10 and 11, the industrialelement/controller 306 (e.g., the I/O module 100) processes an actionrequest (e.g., request for data, control command, firmware/softwareupdate, set point control, application image download, or the like) onlywhen the action request has been signed and/or encrypted by an actionauthenticator 304. This prevents unauthorized action requests from validuser profiles and further secures the system from unauthorized actionrequests coming from invalid (e.g., hacked) profiles. In embodiments, anaction authentication process is implemented as described in U.S. patentapplication Ser. No. 14/519,066, which is incorporated herein byreference in its entirety.

The action authenticator 304 can either be on-site with the actionoriginator 302 (e.g., directly connected device lifecycle managementsystem (“DLM”) 322 or secured workstation 326) or remotely located(e.g., DLM 322 connected via the network 318). In general, the actionauthenticator 304 includes a storage medium with a private key storedthereon and a processor configured to sign and/or encrypt the actionrequest generated by the action originator 302 with the private key. Theprivate key is stored in a memory that cannot be accessed via standardoperator login. For instance, the secured workstation 326 can require aphysical key, portable encryption device (e.g., smart card, RFID tag, orthe like), and/or biometric input for access.

In some embodiments, the action authenticator 304 includes a portableencryption device such as a smart card 324 (which can include a securedmicroprocessor). The advantage of using a portable encryption device isthat the entire device (including the privately stored key and processorin communication therewith) can be carried with an operator or user thathas authorized access to an interface of the action originator 302.Whether the action authentication node 304 accesses the authenticationpath 300 via secured or unsecured workstation, the action request fromthe action originator 302 can be securely signed and/or encrypted withinthe architecture of the portable encryption device instead of apotentially less secure workstation or cloud-based architecture. Thissecures the industrial control system 200 from unauthorized actions. Forinstance, an unauthorized person would have to physically takepossession of the smart card 324 before being able to authenticate anyaction requests sent via the action originator 302.

Furthermore, multiple layers of security can be employed. For example,the action authenticator 304 can include a secured workstation 326 thatis only accessible to sign and/or encrypt action requests via smart cardaccess or the like. Additionally, the secured workstation 326 can beaccessible via a biometric or multifactor cryptography device 328 (e.g.,fingerprint scanner, iris scanner, and/or facial recognition device). Insome embodiments, a multifactor cryptography device 328 requires a validbiometric input before enabling the smart card 324 or other portableencryption device to sign the action request.

The I/O module 100 or any other industrial element/controller 306 beingdriven by the action originator 302 is configured to receive the signedaction request, verify the authenticity of the signed action request,and perform a requested action when the authenticity of the signedaction request is verified. In some embodiments, the industrialelement/controller 306 includes a storage medium 330 (e.g., SD/micro-SDcard, HDD, SSD, or any other non-transitory storage device) configuredto store the action request (e.g., application image, control command,and/or any other data sent by the action originator). The I/O module 100or any other industrial element/controller 306 further includes aprocessor 332 (e.g., controller 106) that performs/executes the actionrequest (i.e., performs the requested action) after the signature isverified. In some embodiments, the action request is encrypted by theaction originator 302 and/or the action authenticator 332 and must alsobe decrypted by the processor 332 before the requested action can beperformed. In implementations, the I/O module 100 or any otherindustrial element/controller 306 includes a virtual key switch 334(e.g., a software module running on the processor 332) that enables theprocessor 332 to perform the requested action only after the actionrequest signature is verified and/or after the action request isdecrypted. In some embodiments, each and every action or each one of aselection of critical actions must clear the authentication path beforebeing run on the I/O module 100 or any other industrialelement/controller 306.

FIG. 12 shows a flow diagram of an example process 400 of authenticatingan action request via an action authentication path, such as actionauthentication path 300 described herein. In implementations, the method400 can be manifested by the industrial control system 200 and/orauthentication path 300 of the industrial control system 200. The method400 includes: (402) originating an action request (e.g., via anoperator/engineering interface 308/310 or a remote/local applicationinterface 316/320); (404) signing the action request with the actionauthenticator 304; (412) optionally encrypting the action request withthe action authenticator 304; (406) sending or downloading the signedaction request to an I/O module 100 or any other industrialelement/controller 306; (408) verifying the authenticity of the signedaction request; (414) optionally decrypting the action request with theI/O module 100 or any other industrial element/controller 306; and (410)performing a requested action with the I/O module 100 or any otherindustrial element/controller 306 when the authenticity of the signedaction request is verified.

For enhanced security, the I/O module 100 or any other industrialelement/controller 306 can be further configured to perform anauthentication sequence with the action authenticator 304 (e.g., with asmart card 324 or the like) before the requested action is run by theI/O module 100 or any other industrial element/controller 306. Forexample, the so-called “handshake” can be performed prior to step 410 oreven prior to step 406. In some embodiments, the signature andverification steps 404 and 408 can be completely replaced with a moreintricate authentication sequence. Alternatively, the authenticationsequence can be performed as an additional security measure to augmentthe simpler signature verification and/or decryption measures.

In some embodiments, the authentication sequence implemented by the I/Omodule 100 or any other industrial element/controller 306 can include:sending a request datagram to the action authenticator 304, the requestdatagram including a first nonce, a first device authentication keycertificate (e.g., a first authentication certificate that contains adevice authentication key), and a first identity attribute certificate;receiving a response datagram from the action authenticator 304, theresponse datagram including a second nonce, a first signature associatedwith the first and second nonces, a second device authentication keycertificate (e.g., a second authentication certificate that contains adevice authentication key), and a second identity attribute certificate;validating the response datagram by verifying the first signatureassociated with the first and second nonces, the second deviceauthentication key certificate, and the second identity attributecertificate; and sending an authentication datagram to the actionauthenticator 304 when the response datagram is valid, theauthentication datagram including a second signature associated with thefirst and second nonces.

Alternatively, the action authenticator 304 can initiate the handshake,in which case the authentication sequence implemented by the I/O module100 or any other industrial element/controller 306 can include:receiving a request datagram from the action authenticator 304, therequest datagram including a first nonce, a first device authenticationkey certificate, and a first identity attribute certificate; validatingthe request datagram by verifying the first device authentication keycertificate and the first identity attribute certificate; sending aresponse datagram to the action authenticator 304 when the requestdatagram is valid, the response datagram including a second nonce, afirst signature associated with the first and second nonces, a seconddevice authentication key certificate, and a second identity attributecertificate; receiving an authentication datagram from the actionauthenticator 304, the authentication datagram including a secondsignature associated with the first and second nonces; and validatingthe authentication datagram by verifying the second signature associatedwith the first and second nonces.

The handshake or authentication sequence that can be implemented by theI/O module 100 or any other industrial element/controller 306 and theaction authenticator 304 is further described in U.S. patent applicationSer. No. 14/519,047, which is fully incorporated herein by reference.Those skilled in the art will appreciate the applicability of thehandshake between redundant communications/control modules 106 to thehandshake described herein between the I/O module 100 or any otherindustrial element/controller 306 and the action authenticator 304.

Each of the action originator 302, the action authenticator 304, and theI/O module 100 or any other industrial element/controller 306 caninclude circuitry and/or logic enabled to perform the functions oroperations (e.g., blocks of method 400 and the authentication sequence)described herein. For example, each of the action originator 302, theaction authenticator 304, and the I/O module 100 or any other industrialelement/controller 306 can include one or more processors that executeprogram instruction stored permanently, semi-permanently, or temporarilyby a non-transitory machine readable medium such as, but not limited to:a hard disk drive (HDD), solid-state disk (SDD), optical disk, magneticstorage device, flash drive, or SD/micro-SD card.

As discussed above, two or more I/O modules 100 may be connected inparallel with one another, and may be capable of communicating with oneanother. In some embodiments, for further security, the I/O modules 100are configured to perform an authentication sequence or handshake toauthenticate one another at predefined events or times including such asstartup, reset, installation of a new I/O module 100, replacement of anI/O module 100, periodically, at scheduled times, and so forth. Bycausing the I/O modules 100 to authenticate one another, counterfeit ormaliciously introduced I/O modules 100 can be avoided.

FIG. 13 shows exemplary datagrams 500 transmitted between two I/Omodules 100 (e.g., a first I/O module 100A and a second I/O module 100B)in performance of the authentication sequence. To initiate theauthentication sequence, the first I/O module 100A is configured totransmit a request datagram 502 to the second I/O module 100B. Inimplementations, the request datagram 502 includes a first plain textnonce (NonceA), a first device authentication key certificate (CertDAKA)containing a first device authentication key (DAKA), and a firstidentity attribute certificate (IACA). In some embodiments, the firstI/O module 100A is configured to generate the first nonce (NonceA) witha true random number generator (hereinafter “TRNG”) and concatenate orotherwise combine the first nonce (NonceA), the first deviceauthentication key certificate (CertDAKA), and the first identityattribute certificate (IACA) to generate the request datagram 502. Insome embodiments, the first device authentication key certificate(CertDAKA) and the first identity attribute certificate (IACA) arelocally stored by the first I/O module 100A. For example, thecertificates may be stored in a local memory (e.g., ROM, RAM, flashmemory, or other non-transitory storage medium) of the first I/O module100A.

The second I/O module 100B is configured to validate the requestdatagram by verifying the first device authentication key certificate(CertDAKA) and the first identity attribute certificate (IACA) withpublic keys that are generated by a device lifecycle management system(DLM) or derived utilizing crypto library functions. In this regard, thepublic keys may be stored in SRAM or another local memory of the I/Omodule 100 and used with crypto library functions to verify orcryptographically sign exchanged data, such as the nonces exchangedbetween the I/O modules 100. In some embodiments, the second I/O module100B may verify the certificates with an elliptic curve digital signingalgorithm (hereinafter “ECDSA”) or other verification operation. In someembodiments, the second I/O module 100B may be further configured tovalidate the certificate values from plain text values by verifying thefollowing: certificate type is device authentication key (hereinafter“DAK”) or identity attribute certificate (hereinafter “IAC”) for eachcertificate; IAC names match, DAK certificate module type matches moduletype argument; and/or microprocessor serial number (hereinafter “MPSN”)of each certificate in the message payload match each other. In someembodiments, the second I/O module 100B may be further configured toverify the DAK and IAC certificates are not in a local revocation list(e.g., a list or database including revoked and/or invalidcertificates). When the second I/O module 100B fails to validate therequest datagram, the second I/O module 100B may generate an errormessage, partially or completely disable the first I/O module 100A,and/or discontinue or restrict communications to/from the first I/Omodule 100A.

Responsive to a valid request datagram 502, the second I/O module 100Bis configured to transmit a response datagram 504 to the first I/Omodule 100A. In implementations, the response datagram 504 includes asecond plain text nonce (NonceB), a first signature associated with thefirst and second nonces (SigB[NonceA∥NonceB]), a second deviceauthentication key certificate (certDAKB) containing a second deviceauthentication key (DAKB), and a second identity attribute certificate(IACB). In some embodiments, the second I/O module 100B is configured togenerate the second nonce (NonceB) with a TRNG, concatenate or otherwisecombine the first nonce (NonceA) and the second nonce (NonceB), and signthe concatenated/combined nonces with a private key (e.g., DAK) that islocally stored by the second I/O module 100B. The second I/O module 100Bis further configured to concatenate or otherwise combine the secondnonce (NonceB), the first signature associated with the first and secondnonces (SigB[NonceA∥NonceB]), the second device authentication keycertificate (certDAKB), and the second identity attribute certificate(IACB) to generate the response datagram 504. In some embodiments, thesecond device authentication key certificate (CertDAKB) and the secondidentity attribute certificate (IACB) are locally stored by the secondI/O module 100B. For example, the certificates may be stored in a localmemory (e.g., ROM, RAM, flash memory, or other non-transitory storagemedium) of the second I/O module 100B.

The first I/O module 100A is configured to validate the responsedatagram by verifying the second device authentication key certificate(CertDAKB) and the second identity attribute certificate (IACB) withpublic keys that are locally stored or retrieved from a crypto libraryutilizing ECDSA or another verification operation. In some embodiments,the first I/O module 100A may be further configured to validate thecertificate values from plain text values by verifying the following:IAC & DAK certificates have matching MPSNs, IAC names match, certificatetypes are correct on both certificates (IAC & DAK), the correct issuername is on both certificates, DAK module type is the correct type (e.g.,check to see if module type=communications/control module). In someembodiments, the first I/O module 100A may be further configured toverify the DAK and IAC certificates are not in a local revocation list.

To validate the response datagram, the first I/O module 100A may befurther configured to verify the first signature associated with thefirst and second nonces (sigB[NonceA∥NonceB]). In some embodiments, thefirst I/O module 100A is configured to verify the first signature(sigB[NonceA∥NonceB]) by concatenating the first locally stored nonce(NonceA) and the second plaintext nonce (NonceB) received from thesecond I/O module 100B, verfying the first cryptographic signature(sigB[NonceA∥NonceB]) with a public device authentication key (e.g.,using DAKB from certDAKB), and comparing the locally generatedconcatenation of the first nonce and the second nonce with thecryptographically verified concatenation of the first nonce and thesecond nonce. When the first I/O module 100A fails to validate theresponse datagram, the first I/O module 100A may generate an errormessage, partially or completely disable the second I/O module 100B,and/or discontinue or restrict communications to/from the second I/Omodule 100B.

The first I/O module 100A is further configured to transmit anauthentication datagram 506 to the second I/O module 100B when theresponse datagram 504 is valid. In implementations, the authenticationdatagram 506 includes a second signature associated with the first andsecond nonces (sigA[NonceA∥NonceB]). In some embodiments, the first I/Omodule 100A is configured to sign the locally generated concatenation ofthe first and second nonces a private key (e.g., DAK) that is locallystored by the first I/O module 100A. When the response datagram isinvalid, the authentication datagram 506 may be replaced with a “failed”authentication datagram 506 including a signature associated with thesecond nonce and an error reporting (e.g., “failure”) message(sigA[NonceB∥Error]) generated by the first I/O module 100A.

Responsive to the authentication datagram 506, the second I/O module100B may be further configured to transmit a responsive authenticationdatagram 508 to the first I/O module 100A. In implementations, theresponsive authentication datagram 508 includes a signature associatedwith the first nonce and an error reporting (e.g., “success” or“failure”) message (sigB[NonceA∥Error]) generated by the second I/Omodule 100B. In some embodiments, the second I/O module 100B isconfigured to validate the authentication datagram 506 by verifying thesecond signature associated with the first and second nonces(sigA[NonceA∥NonceB]). In some embodiments, the second I/O module 100Bis configured to verify the second signature (sigA[NonceA∥NonceB]) byconcatenating the first plaintext nonce (NonceA) received from the firstI/O module 100A and the second locally stored nonce (NonceB), verifyingthe second cryptographic signature (sigA[NonceA∥NonceB]) with a publicdevice authentication key (e.g., using DAKA from certDAKA), andcomparing the locally generated concatenation of the first nonce and thesecond nonce with the cryptographically verified concatenation of thefirst nonce and the second nonce. In addition to the error reportingmessage, when the second I/O module 100B fails to validate theauthentication datagram, the second I/O module 100B may partially orcompletely disable the first I/O module 100A, and/or discontinue orrestrict communications to/from the first I/O module 100A.

In implementations where the I/O modules 100 are arranged according to a“master-slave” configuration, the master (e.g., the first I/O module100A) may be configured to authenticate each slave. In the event of afailed authentication, the master may at least partially disable orrestrict communications to/from the unauthenticated slave.Alternatively, two or more slave I/O modules 100 and/or two or more I/Omodules 100 operating in parallel without a master may authenticate oneanother. A failed authentication may result in both devices or apseudo-secondary device (e.g., non-initiating I/O module) beingpartially or completely disabled. For example, two or more redundant I/Omodules 100 can be disabled should they fail to successfully completethe authentication sequence at startup or another predefined time/event.

Each I/O module 100 may include circuitry and/or logic enabled toperform the functions described herein. For example, the controller 106may be configured to execute program instructions stored permanently,semi-permanently, or temporarily by a non-transitory machine readablemedium 108 such as a hard disk drive (HDD), solid-state disk (SDD),optical disk, magnetic storage device, flash drive, or the like.Accordingly, the controller 106 may be configured to carry out anauthentication initiator sequence 600 and/or an authentication respondersequence 700 illustrated in FIGS. 14 and 15, respectively.

Referring to FIG. 14, the authentication initiator sequence 600implemented by the first I/O module 100A (i.e., the initiator) mayinclude: (602) sending a request datagram to a second I/O module 100B(i.e. the responder), the request datagram including a first nonce, afirst device authentication key certificate, and a first identityattribute certificate; (604) receiving a response datagram from thesecond I/O module 100B, the response datagram including a second nonce,a first signature associated with the first and second nonces, a seconddevice authentication key certificate, and a second identity attributecertificate; (606) validating the response datagram by verifying thefirst signature associated with the first and second nonces, the seconddevice authentication key certificate, and the second identity attributecertificate; and (610) sending an authentication datagram to the secondI/O module 100B when the response datagram is valid, the authenticationdatagram including a second signature associated with the first andsecond nonces; or (608) sending a failed authentication datagram to thesecond I/O module 100B when the response datagram is invalid, the failedauthentication datagram including a signature associated with the secondnonce and an error message.

Referring to FIG. 15, the authentication responder sequence 700 (e.g.,implemented by the second I/O module 100B) may include: (702) receivinga request datagram from the first I/O module 100A, the request datagramincluding a first nonce, a first device authentication key certificate,and a first identity attribute certificate; (704) validating the requestdatagram by verifying the first device authentication key certificateand the first identity attribute certificate; (706) sending a responsedatagram to the first I/O module 100A when the request datagram isvalid, the response datagram including a second nonce, a first signatureassociated with the first and second nonces, a second deviceauthentication key certificate, and a second identity attributecertificate; (708) receiving an authentication datagram from the firstI/O module 100A, the authentication datagram including a secondsignature associated with the first and second nonces; (710) validatingthe authentication datagram by verifying the second signature associatedwith the first and second nonces; and (712) sending a responsiveauthentication datagram to the first I/O module 100A, the responsiveauthentication datagram including a signature associated with the firstnonce and a success or failure message.

In some embodiments, the I/O modules 100 can be further configured toauthenticate with and/or be authenticated by other elements of theindustrial control system 200, such as communications/control modules214, field devices 217 (e.g. sensors 218 or actuators 220), powermodules 232, physical interconnect devices, switches, and the like.Industrial controllers/elements can be configured to authenticate oneanother or other devices by performing a sequence or handshake such asthe authentication sequence (between redundant I/O modules 100)described above. For example, the I/O module 100 can be configured toperform an authentication sequence (e.g., as described above) with acommunications/control module 214 or a field device 217. It is furthercontemplated that, communicatively coupled field devices 217 (e.g.,sensors 218 or actuators 220) can also be configured to authenticatewith each other in a manner similar to the authentication processdescribed above.

It should be understood that any of the functions described herein canbe implemented using hardware (e.g., fixed logic circuitry such asintegrated circuits), software, firmware, manual processing, or acombination thereof. Thus, the blocks, operations, functions, or stepsdiscussed in the above disclosure generally represent hardware (e.g.,fixed logic circuitry such as integrated circuits), software, firmware,or a combination thereof. In the instance of a hardware configuration,the various blocks discussed in the above disclosure may be implementedas integrated circuits along with other functionality. Such integratedcircuits may include all of the functions of a given block, system, orcircuit, or a portion of the functions of the block, system, or circuit.Further, elements of the blocks, systems, or circuits may be implementedacross multiple integrated circuits. Such integrated circuits maycomprise various integrated circuits, including, but not necessarilylimited to: a monolithic integrated circuit, a flip chip integratedcircuit, a multichip module integrated circuit, and/or a mixed signalintegrated circuit. In the instance of a software implementation, thevarious blocks discussed in the above disclosure represent executableinstructions (e.g., program code) that perform specified tasks whenexecuted on a processor. These executable instructions can be stored inone or more tangible computer readable media. In some such instances,the entire system, block, or circuit may be implemented using itssoftware or firmware equivalent. In other instances, one part of a givensystem, block, or circuit may be implemented in software or firmware,while other parts are implemented in hardware.

Although the subject matter has been described in language specific tostructural features and/or process operations, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

1.-21. (canceled)
 22. A control system comprising: a control moduleconfigured to mate with a support frame; and an input/output moduleconfigured to mate with the support frame, the input/output modulecommunicatively coupled with the control module, the input/output moduleincluding a plurality of communication channels within the input/outputmodule, each channel of the plurality of communication channelsconfigured to connect to one or more field devices, the input/outputmodule further including switch fabric within the input/output, theswitch fabric configured to selectively facilitate connectivity betweenthe control module and the one or more field devices via the pluralityof communication channels, the input/output module further including acontroller coupled to the switch fabric, the controller configured toconcurrently communicate over the plurality of communication channels,the plurality of communication channels using multiple communicationstandards running concurrently on respective channels of the pluralityof communication channels, the multiple communication standardscomprising at least two distinct communication standards, the at leasttwo distinct communication standards including at least one of anEthernet bus, an H1 field bus, a Process Field Bus (PROFIBUS), a HighwayAddressable Remote Transducer (HART) bus, a Modbus, and an ObjectLinking and Embedding for Process Control Unified Architecture (OPC UA)bus.
 23. The control system of claim 22, wherein the control module isconfigured to assign the input/output module a unique identifierassociated with a physical location where the input/output module isphysically connected to the control module.
 24. The control system ofclaim 22, further comprising a power module for supplying electricalpower to the input/output module.
 25. The control system of claim 22,wherein the input/output module is configured to supply electrical powerto at least one field device via a respective channel of the pluralityof communication channels.
 26. The control system of claim 22, whereinthe plurality of communication channels comprise a plurality of Ethernetchannels.
 27. The control system of claim 22, wherein the plurality ofcommunication channels includes at least two of: an Ethernet bus, an H1field bus, a Process Field Bus (PROFIBUS), a Highway Addressable RemoteTransducer (HART) bus, a Modbus, and an Object Linking and Embedding forProcess Control Unified Architecture (OPC UA) bus.
 28. The controlsystem of claim 22, wherein the input/output module is operable as atleast one of an Object Linking and Embedding for Process Control UnifiedArchitecture (OPC UA) client or an OPC UA server.
 29. The control systemof claim 22, wherein the input/output module is configured tosynchronize the one or more field devices according to an IEEE 1588timing protocol.
 30. The control system of claim 22, further comprisinga device lifetime management system in communication with theinput/output module, wherein the device lifetime management system isconfigured to authenticate the one or more field devices.
 31. Thecontrol system of claim 22, further comprising: a serial communicationsinterface configured for connecting the input/output module to thecontrol module, the serial communications interface connecting theinput/output module in parallel with a second input/output module, theserial communications interface configured for transmitting informationbetween the input/output module and the control module; and a parallelcommunications interface configured for separately connecting theinput/output module to the control module, the parallel communicationsinterface configured for transmitting information between theinput/output module and the control module, and transmitting informationbetween the input/output module and the second input/output module. 32.An input/output module comprising: an encasement configured to mate witha support frame; a plurality of communication channels within theencasement, each channel of the plurality of communication channelsconfigured to connect to one or more field devices; a switch fabricwithin the encasement, the switch fabric configured to selectivelyfacilitate connectivity between an external control module and the oneor more field devices via the plurality of communication channels; and acontroller coupled to the switch fabric, the controller configured toconcurrently communicate over the plurality of communication channels,the plurality of communication channels using multiple communicationstandards running concurrently on respective channels of the pluralityof communication channels, the multiple communication standardscomprising at least two distinct communication bus standards.
 33. Theinput/output module of claim 32, wherein the plurality of communicationchannels comprises a plurality of Ethernet channels.
 34. Theinput/output module of claim 33, wherein the input/output module isconfigured to supply electrical power to at least one field device via arespective Ethernet channel of the plurality of Ethernet channels. 35.The input/output module of claim 32, wherein the multiple communicationstandards include at least two of: an Ethernet bus, an H1 field bus, aProcess Field Bus (PROFIBUS), a Highway Addressable Remote Transducer(HART) bus, a Modbus, or an Object Linking and Embedding for ProcessControl Unified Architecture (OPC UA) bus.
 36. The input/output moduleof claim 32, wherein the controller is configured to run at least one ofan Object Linking and Embedding for Process Control Unified Architecture(OPC UA) client communications/control protocol or an OPC UA servercommunications/control protocol.
 37. The input/output module of claim32, further comprising: a serial communications port configured forconnecting the input/output module to the control module in parallelwith a second input/output module, the serial communications portconfigured for transmitting information between the input/output moduleand the control module; and a parallel communications port configuredfor separately connecting the input/output module to the control module,the parallel communications port configured for transmitting informationbetween the input/output module and the control module, and transmittinginformation between the input/output module and the second input/outputmodule.
 38. The input/output module of claim 37, wherein at least one ofthe serial communications port or the parallel communications portcomprises an electromagnetic connector forming a first magnetic circuitportion, including: a first core member; and a first coil disposed ofthe first core member, the electromagnetic connector configured to matewith a second electromagnetic connector, the second electromagneticconnector configured to form a second magnetic circuit portion andcomprising a second core member and a second coil disposed of the secondcore member, the first core member and the second core member configuredto couple the first coil to the second coil with a magnetic circuitformed from the first magnetic circuit portion and the second magneticcircuit portion when the electromagnetic connector is mated with thesecond electromagnetic connector, the magnetic circuit configured toinduce a signal in the first coil when the second coil is energized. 39.The input/output module of claim 38, wherein the first coil comprises aplanar winding disposed of a printed circuit board.
 40. The input/outputmodule of claim 38, wherein the first core member comprises an E-shapedcore member.
 41. The input/output module of claim 38, wherein themagnetic circuit formed from the first core member and the second coremember comprises an air gap.